Managing Information About Relationships in a Social Network via a Social Timeline

ABSTRACT

A system, method, and computer program for generating a social timeline is provided. A plurality of data items associated with at least one relationship between users associated with a social network is received, each data item having an associated time. The data items are ordered according to the at least one relationship. A social timeline is generated according to the ordered data items.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.11/646,206, filed Dec. 26, 2006, which claims the benefit of U.S.Provisional Application No. 60/753,810, filed Dec. 23, 2005. Each of theforegoing applications is incorporated by reference in its entirety.

BACKGROUND

The present invention relates generally to social networking, and moreparticularly to systems and methods for generating a social timeline.

Conventionally, people have networked with one another by joining socialclubs, attending social events, meeting friends through other friends,and so forth. The Internet has made keeping in touch with friends andacquaintances more convenient for many people. For other people, theInternet provides a social forum for networking and meeting new people.

For many people, the Internet more recently represents the principal wayin which the people meet new friends and remain in touch with existingfriends. Thus, the Internet provides a medium for a complex array ofinteractions between vast numbers of individuals.

In order to facilitate communications between the vast numbers ofindividuals, various social networking websites have developed in recentyears. Social networking websites can provide organizational tools andforums for allowing these individuals to interact with one another viathe social networking website. Many users prefer to limit communicationsto specific groups of other users.

SUMMARY

The present invention provides a system and method for generating asocial timeline. A plurality of data items associated with at least onerelationship between users associated with a social network is received,each data item having an associated time. The data items are orderedaccording to the at least one relationship. A social timeline isgenerated according to the ordered data items.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary environment for socialmapping;

FIG. 2 illustrates an exemplary social network engine;

FIG. 3 illustrates an exemplary friends list;

FIG. 4 illustrates an exemplary relationship editor page;

FIG. 5 illustrates an exemplary social timeline;

FIG. 6 is a flow diagram of an exemplary process for ordering data for asocial timeline; and

FIG. 7 is a flow diagram of an exemplary process for generating a socialtimeline.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an exemplary environment for generating asocial timeline. One or more users 102, such as a user 102A, a user102B, and a user 102N, are in communication with a social network engine106 via a network 104. The social network engine 106 may comprise asocial networking website, one or more servers operating the socialnetworking website, or any other device or application capable ofproviding social networking services via the network 104. The users 102can access the services provided by the social network engine 106 viathe network 104. Optionally, one or more of the users 102 may be able toaccess the social network engine 106 directly.

The users 102 may use a computing device, such as a laptop or desktopcomputer, a cellular telephone, a personal digital assistant (PDA), aset top box, and so forth to access the social network engine 106. Theusers 102 can view data about social network members, view a socialtimeline, enter data about themselves and possibly others, join socialnetwork groups, and so forth. The users 102 are typically members of asocial networking website associated with the social network engine 106,for example, and thus comprise the social network members.

According to exemplary embodiments, a user 102, such as the user 102A,identifies one or more other members associated with the social networkengine 106, such as the user 102B and the user 102N, with which the user102A wants to build a relationship or establish or alter the details ofan existing relationship. Using the social network engine 106, the user102A enters the details about the relationship. The social networkengine 106 then sends data comprising the details from the user 102A tothe other users (i.e., user 102B and user 102N). The user 102B and theuser 102N may then provide input in response to the data. The responsemay, for example, modify the data.

The relationship with the user 102B and the user 102N may confirmed,based on the input, by the social network engine 106. Alternatively, theexistence of the relationship may be denied, according to someembodiments. Any type of confirmation and/or input may be utilized toalter, deny, and/or establish the relationship between the user 102A andthe user 102B and the user 102N.

The relationship may comprise any type of relationship that existsbetween two of the users 102. For example, the user 102A and the user102B may have worked together, been classmates, be related, have dated,and so forth. More than one relationship may exist between the twousers. For example, the user 102A and the user 102B may have both workedtogether and dated.

The data may then be ordered. For example, the user 102A may specifythat the relationship with the user 102B is older than the relationshipwith the user 102N. In other words, the user 102A may enter detaileddata that indicates calendar dates, years, and other timing informationabout the relationship. The social network engine 106 can then order thedata by the indicated times and generate a social timeline based on theordered data. The social timeline may indicate when certain eventsrelated to the relationships occurred, for example, such as in the year2004, the user 102A met the user 102B and traveled with the user 102B toArgentina. Any type of events, details, and other data related to therelationship may be provided by the users 102 and utilized to generatethe social timeline.

Referring now to FIG. 2, an exemplary social network engine isillustrated, such as the social network engine 106 discussed in FIG. 1.A communications interface 202 is provided in association with thesocial network engine 106 for receiving data from and sending data tothe users 102. The users 102 can send any type of data to the socialnetwork engine 106 via the network 104 and vice versa. For example, auser 102 can provide details about relationships with other users 102that the social network engine 106 can utilize to generate the socialtimeline for the user 102, such as the user 102A, based on the details.

Typically, the users 102 access a website associated with the socialnetwork engine 106. For example, the social network engine 106 may hosta social networking website where the users 102 can visit to interactwith one another. The website can display various types of data aboutthe users 102 to one another, such as the social timeline, profileinformation, or relationships a particular user, such as the user 102A,has with other users, such as the user 102B and the user 102N. The users102 may belong to particular communities within the social networkingwebsite, such as communities categorized according to school attended,workplace, geographical location, and so forth.

A social relationship editor module 204 is provided for editing and/orentering the social relationships that the users 102 have with oneanother. For example, the user 102A can specify a particularrelationship with the user 102B and the user 102N. The user 102B and/orthe user 102N may then be asked to confirm the particular relationshipspecified by the user 102A. Accordingly, each relationship establishedvia the social networking website is verified by two or more of theusers 102 in the relationship. A social relationship editor display pageassociated with the social relationship editor module 204 is discussedfurther in association with FIG. 4.

The social relationship editor module 204 can track the one or morerelationships between the users 102. The social relationship editormodule 204 can also generate and send communications to the users 102 toconfirm the relationships identified. As discussed herein, the users 102are typically members of the social networking website. Accordingly, theusers 102 interact with one another via the social network websiteassociated with the social network engine 106 and can identifyrelationships with one another in order to facilitate the interactions,or for any other reason.

The social relationship editor module 204 may also be utilized by theusers 102 to enter data about the relationships with other users 102, asdiscussed herein. The data may then be utilized to generate the socialtimeline for the users 102, such as what events happened each day,month, or year to the user 102A.

A relationship storage module 206 is provided for storing one or moredatabases including the relationships between the users 102. Therelationship storage module 206 can utilize any type of storage deviceor medium to store the database. For example, the relationship storagemodule 206 can store the databases in hard drives, on CD ROMS, in DRAM,and so forth. Any type of storage device or storage medium for storinginformation about the relationships, profile data associated with theusers 102, or any other information associated with the users 102, iswithin the scope of various embodiments. According to some embodiments,the relationship storage module 206 can store the social timelinegenerated for each of the users 102.

A social timeline module 208 is also provided in association with thesocial network engine 106. The social timeline module 208 utilizes therelationship data provided by the users 102. The data provided by theusers 102 about various relationships is then ordered by the times therelationships occurred, or events associated with the relationshipsoccurred, as indicated by the users 102. For example, the user 102A mayindicate that the user 102A took a class with user 102B in the Fall of2003. The data about the class is then ordered in relation to other dataprovided by the user 102A and the social timeline for the user 102A isgenerated.

The user 102A may be able to request, via a button, portal, link, and soforth, a display page showing the social timeline associated with theuser 102A. Other users 102 may also be able to request the socialtimeline for the user 102A. A different social timeline may be generatedfor different communities associated with the user 102A, such as onesocial timeline for the workplace community, another social timeline fora college community, etc.

A display module 210 may be associated with the social network engine106. The display module 210 may generate a display for displaying thesocial timeline to the users 102. The social timeline may be displayedto the user 102 that provides the social timeline data items, such asevents and timeframes associated with the events, or the social timelinemay be displayed to other users 102 that want to see one another'ssocial timelines. The user 102A may adjust privacy settings to identifyother users 102 or groups of users 102 that can access the socialtimeline for the user 102A.

Although FIG. 2 shows various modules associated with the social networkengine 106 (e.g., the communications interface 202, the socialrelationship editor module 204, the relationship storage module 206, andthe social timeline module 208), fewer or more modules may be associatedwith the social network engine 106 and still fall within the scope ofvarious embodiments.

FIG. 3 illustrates an exemplary friends list 300. The friends list 300may be displayed on a page associated with the social network engine106. The friends list 300 may be selected by the users 102 via a friendslist tab 302. A social timeline tab 304 may also be selected. The socialtimeline tab 304 may display events associated with the relationshipswith friends on the friends list 300 according to a timeline.

A pictorial or graphical representation 306 for each of the users 102may be included as part of the friends list 300. For example, the user102A may utilize a photo of the user A 102, while the user 102B mayutilize a cartoon character to represent the user 102B. Any type ofpicture, photo, graphic, icon, symbol, and so forth may be utilized torepresent the users 102 via the pictorial or graphical representation306.

Biographical data 308 is displayed about each of the users 102 that arelisted. For example, the name, status, year of graduation, field ofstudy, and so forth may be displayed as the biographical data 308 foreach of the users 102. Any type of data about the listed users 102 maycomprise the biographical data 308.

A user action area 310 may be associated with the friends lists 300 andmay be displayed in association with each of the users 102. In FIG. 3,the user action area 310 is displayed to the right of the biographicaldata 308 for each of the users 102. However, the user action area 310,the biographical data 308, and/or the pictorial/graphical representation306 may be displayed anywhere. For example, the pictorial/graphicalrepresentation 306 may be accessed, check-marked, highlighted, and soforth in order to display the user action area 310.

The user action area 310 allows the users 102 to select one or moreactions to perform in association with a particular user, such as theuser 102A, about which the biographical data 306 is being viewed. Forexample, the users 102 can choose to send the users 102 an email orother message via the “send message” function, to utilize a “poke her!”function to be directed to a pop-up or similar screen, confirming thatthe user 102 wishes to “poke” a displayed user. An announcement may besent to the displayed user informing the displayed user that thedisplayed user has been “poked” by another user 102.

The user action area 306 may also allow the users 102 to utilize a “viewfriends” function” in order to view the data about friends of the users102, to utilize a “view photos” function to view photos associated withthe user, and/or an “add to friends” function to request addition to afriends group of the user 102. Various other options may be accessed viathe user action area 306. For example, the users 102 may be able toaccess stories about a particular user, such as the user B 102B, via theuser action area 306.

For example, the users 102 can choose to send the users 102 an email orother message via the “send message” function, to utilize a “poke her!”function to be directed to a pop-up or similar screen, confirming thatthe user 102 wishes to “poke” a displayed user. An announcement may besent to the displayed user informing the displayed user that thedisplayed user has been “poked” by another user 102.

The user action area 306 may also allow the users 102 to utilize a “viewfriends” function” in order to view the data about friends of the users102, to utilize a “view photos” function to view photos associated withthe user, and/or an “add to friends” function to request addition to afriends group of the user 102. Various other options may be accessed viathe user action area 306. For example, the users 102 may be able toaccess stories about a particular user, such as the user B 102B, via theuser action area 306.

The friends list 300 may be utilized for displaying any type of dataabout the users 102. The friends list 300 shown in FIG. 3 is anexemplary display page for displaying data about various users belongingto a community. Profile data about individual users or groups of usersis shown via the friends list 300. Data about the users 102 belonging tovarious communities, stories about the users 102, and so forth, may alsobe displayed via the friends list 300, or any other display page.

The friends list 300 in FIG. 3 may also be utilized, according toexemplary embodiments, to display a social timeline associated with thefriends on the friends list 300. The friends list 300 may be generatedby the social relationship editor module 304 and be displayed inresponse to a search or filter function initiated by the user 102A. Asdiscussed herein, the data about the users 102 for the friends list 300may be stored in a database by the relationship storage module 206 oranother storage module (not shown) for storing data about the users 102.

The friends list 300 may be utilized to display a directory of the users102, a collection of the users 102, a directory of establishedrelationships associated with the user 102A, or any other informationabout the users 102. As discussed herein, any of the data associatedwith the users 102 may be displayed utilizing the friends list 300 orany other display mechanism associated with the social network engine106.

The friends list 300 can also display the users 102 in an ascending ordescending order according to a chronology associated with therelationships the users 102 have with other users, such as by generatingthe social timeline discussed herein. For example, the user 102N may bedisplayed before the user 102B in a listing requested by the user 102Abecause the user 102A has known the user 102N for a longer period oftime than the user 102B. The users 102 can be displayed according tocommon groups, association with common events, situations, oroccurrences, and so forth.

FIG. 4 illustrates an exemplary relationship editor page 400. Therelationship editor page 400 illustrated in FIG. 4 can be utilized toquestion the users 102 about the relationships with other users 102. Therelationship editor page 400 may be utilized to learn details about therelationships, such as timing information for generating the socialtimeline. The relationship editor page 400 may be sent in response to arequest from a particular user, such as the user 102A, to form orotherwise establish a relationship with another user, such as the user102B, and/or to edit details about the relationship, such as providingdetails about specific events and/or timeframes associated with thespecific events.

A relationship inquiry 402 may be utilized to establish the subjectmatter for the relationship editor page 400. For example, FIG. 4illustrates the relationship editor page 400 for the relationshipinquiry 402 “How do you know John Do?” However, the relationship inquiry402 may comprise any inquiry, such as “Is the information provided byJohn Do about your relationship accurate?” Any type of relationshipinquiry 402 may be provided in association with the relationship editorpage 400.

A relationship type identifier 404 may be displayed for allowing a user102 to select and/or identify the relationship the user 102 has withother users 102. For example, the user 102A may select that the user102A lived with the user 102B, worked with the user 102B, and/or knowsthe user 102B through a friend. One or more of the relationshipidentifiers 404 may be selected. As discussed herein, the users 102 mayhave more than one relationship.

A relationship details identifier 406 allows the users 102 to furtherspecify the nature of the relationship. For example, the relationshipdetails identifier 406 may establish where the users 102 lived together,where the users 102 worked together, which friends the users 102 have incommon, and so forth. Although only one relationship details identifier406 is illustrated for each relationship type identifier 404, more thanone relationship details identifier 406 associated with each of therelationship type identifiers 404 may be provided.

A timeframe identifier 408 may also be provided in association with therelationship editor page 400. The timeframe identifier 408 may beutilized to establish a time or timeframe associated with therelationship type identifier 404. For example, the timeframe identifier408 can specify when the users 102 lived together, worked together,dated, and so forth. The timeframe identifier 408 data may then beordered and utilized to generate the social timeline, discussed herein.

The relationship inquiry 402, the relationship type identifier 404, therelationship details identifier 406, and/or the timeframe identifier 408may be selectable via a drop down menu, a text entry box, a check box,and/or via any other selection method or combination of selectionmethods. According to some embodiments, the relationship inquiry 402 ispre-populated with selections when sent to the users 102 with whomconfirmation of the relationship is sought. Further, the relationshipeditor page 400 can be automatically populated, partially or wholly,utilizing data already stored about the users 102 and/or therelationships the users 102 have established with one another onprevious occasions. For example, the relationship editor page 400 can besent to the user 102A to confirm that the timeframe data about therelationship specified by the relationship editor page 400 is correct.

The arrangement, presentation, display, and/or subject matter describedin connection with FIGS. 3 and 4 may vary and still remain within thescope of various embodiments. Additional timeframe questions may beutilized in association with the social relationship page 400 oradditional types of the biographical data 304 may be displayed via thefriends list 300.

For example, the user 102A may complete the relationship editor page 400by selecting from the relationship inquiry 402, the relationship typeidentifier 404, the relationship details identifier 406, the timeframeidentifier 408, and/or any other identifiers that may be provided viathe relationship editor page 400, in order to provide details about therelationship the user 102A has with the user 102B. The user 102B maythen be sent the pre-populated relationship editor page 400 and asked toconfirm the data provided by the user 102A. The user 102B can confirmthe accuracy of the data on the relationship editor page 400, modify thedata on the relationship editor page 400, add to the data on therelationship editor page 400, and/or deny the accuracy of the data onthe relationship editor page 400.

The details about the relationship established via the relationshipeditor page 400 can be stored by the relationship storage module 206 anda relationship database utilized to access timeframe informationprovided by the user 102 about each data item to organize the data itemsprovided by the users 102 associated with the relationships between theusers 102 and to generate the social timeline. Alternatively, the socialtimelines or timeline data from the user 102B may be utilized topopulate times for the data items associated with the user 102A, such aswhen the user 102A fails to provide the times associated with the dataitems.

The subject matter of the inquiries and the data associated with therelationship editor page 400 may include any topics, such as membershipin a club, a team, a church, etc.; common courses, classes,institutions, programs of study, etc.; common travels, journeys,adventures, parties, conferences, etc.; common familial relationships,friends, acquaintances, romantic partners or interests, musicalinterests, restaurants, bars, pubs, etc.; whether two or more of theusers 102 met randomly, accidentally, purposefully, via onlineactivities, etc.; and/or whether two or more of the users 102 have nevermet, etc. Any type of data can be established via the relationshipeditor page 400, as discussed herein.

As discussed herein, a confirmation request may be sent to the users 102in response to completion of the relationship editor page 400. Thesocial relationship editor module 204 can send a communication, forexample, to the user 102B that the user 102A selected the user 102B as aperson the user 102A may know or with whom the user 102A wishes toestablish a relationship. The user 102B may elect to confirm the dataprovided by the user 102A, adjust or edit the data, send a message tothe user 102A regarding the relationship, deny the existence of therelationship, add data about the relationship, and so forth. If the user102B edits or adds to the data, the user 102A may be asked to confirmthe added or edited data, according to exemplary embodiments.

According to some embodiments, the user 102A may complete portions ofthe relationship editor page 400, while leaving other portions for theuser 102B to complete. For example, the user 102A may want the user 102Bto complete portions of the relationship editor page 400 describingtimeframes for the relationship between the user 102A and the user 102B.

Referring to FIG. 5, an exemplary social timeline page 500 isillustrated. The social timeline page 500 may be accessed via the socialtimeline tab 304 discussed in FIG. 3 or in any other manner, such as viaa link, a button, a search request, and so forth.

A time identifier 502 is displayed on the social timeline page 500. Thetime identifier 502 indicates the time in which events or other dataitems associated with the user 102A may be displayed. The socialtimeline page 500 for the user 102A may include events associated witheach relationship the user 102A has with other users 102. The data aboutthe relationships, such as classes taken with other users 102, timeframethe user 102A dated another user 102, etc. may be ordered according todates within the time identifier 502, the dates or times for each of thedata items provided by the user 102A. The data may then be displayedwithin the time identifier 502 according to an ascending or descendingorder, for example.

A member list 504 may be displayed according to the time identifier 502,according to some embodiments. As shown in FIG. 5, the member list 504includes names of members grouped under various categories, such ascoworkers, classmates, travel companions, hookups, coursemates,summer/abroad friends, relationships, teammates, and so forth. Themember list 504 may include the names of the members that the user 102Amet in the year specified, for example. Any of the users 102 can clickon, or otherwise access, the name of a particular member (i.e., users102) to access further data about timeframes associated with the user102A's relationship with the particular member, depending upon theprivacy settings selected by the user 102A.

Photos 506 may be displayed in association with each of the timeidentifiers 502 listed as part of the social timeline page 500.According to some embodiments, a user 102 may click on the photos 506 toaccess specific timeframe data about the user 102A's relationship withthe users 102 in the photos 506. Other users 102 can also submit photosthat correlate with the time identifier 502 specified on the socialtimeline page 500. Any type of data can be utilized to generate thesocial timeline and to be displayed via the social timeline page 500.Further, some of the time identifiers 502 may not have any names orevents listed.

The photos 506 may be selected automatically, based on profilesassociated with the users 102 or any other data. The photos 506 may beautomatically updated when a user 102 uploads or otherwise providesupdated photos 506 that the social network engine 106 determines to berelevant to the social timeline. According to some embodiments, the user102 can approve or reject added or edited photos, such as the photos 506shown in FIG. 5, before the photos 506 are uploaded or otherwiseprovided for display with the social timeline.

According to exemplary embodiments, a social timeline for each of theusers 102 may be displayed. The social timeline for each of the users102 may list all of the events or other data pertaining to therelationship a particular user 102, such as the user 102A, has in commonwith one or more of the other users 102. For example, a social timelinefor user A's 102A relationship with the user 102B may be generated. Thesocial timeline in this example may list the events the user 102A andthe user 102B had in common for each year, such as the user 102A and theuser 102B traveled to Mexico together in March of 2003, attended a NewYear's party together in January of 2004, threw a summer barbequetogether in June of 2004, and so forth. The time identifier 502 mayutilize any increment of time, such as day, month, every two years, etc.to display a list of names, events, and so forth associated with theusers 102.

The social timeline module 208 may generate and/or display the socialtimeline page 500, according to some embodiments. However, any module,application, device, or component can generate and/or display the socialtimeline page 500. Any type of data may be utilized to generate thesocial timeline and any process may be employed for generating thesocial timeline, according to some embodiments.

According to some embodiments, some or all of the data from therelationship editor page 400 may be referenced to generate the socialtimeline. The social timeline may be generated automatically ortriggered by the users 102, such as by requesting the social timeline,as discussed herein. Other sources of the data for generating the socialtimeline may also be accessed, such as data from users' 102 profiles,data from stories about the users 102, etc.

The chronological listing in descending order or ascending order may beincluded in the social timeline, as discussed herein. For example, datesmay be listed in descending order down the left hand side of the socialtimeline page 500 in the form of month/date/year. Categories of events,situations, interactions, experiences, and so forth that correspond withthe chronological listing may be generated or utilized to describe thesocial timeline. The data may be formatted or placed in a variety ofpositions on the social timeline page 500. Names of individuals thatcorrespond with various categories may be displayed ion proximity to thecategories, for example, as shown in FIG. 5.

Exemplary embodiments of the social timelines represent tools that mayrepresent the way in which the users 102 interact with one another viathe social networking website or otherwise. The social timeline may bemonitored, edited, and so forth to view the interactions and timeframesassociated with the interactions of the various users 102. The socialtimeline may be utilized, according to some embodiments, to measure theroles and influences the users 102 have on one another.

According to some embodiments, the users 102 may click on a date, name,event, etc. on the social timeline to access additional data about thedate, name, or event. By clicking on, or otherwise accessing, the date,name, event, or other data displayed as part of the social timeline,other users 102 may input data to request a change or update to thesocial timeline. The social timeline may be updated or otherwise editedby the user 102 for which the social timeline is generated, or by otherusers 102, according to some embodiments.

The social timeline may be utilized to generate stories for the users102 according to some embodiments. For example, a story about user B's102B travels in 2005 may be sent to the user 102A based on the fact thatthe user 102B is listed on the social timeline for the user 102A. Anytype of story may be generated or identified for the user 102A based onthe social timeline.

FIG. 6 is a flow diagram of an exemplary process for ordering data for asocial timeline. At step 602, data items and calendar dates associatedwith the data items for one or more relationships between two users arereceived. The user 102A can provide the data items, such as events, andcalendar dates associated with the events about the user 102A'srelationship with 102B.

At step 604, a chronological list of calendar dates in descending orderis generated. For example, the social timeline module 208 may accessdata from the relationship storage module 206 to generate thechronological list. The chronological list may be generated for eachrelationship, for a group of relationships, such as the user A's 102Acollege community and work community, and/or for any other relationship.

The chronological list may include all of the data about therelationships provided by the user 102 for whom the social timeline isgenerated and/or the data from other users 102 with which the user 102has relationships. For example, the user 102A may indicate that the user102A has a relationship with the user 102B, but the data from the user102B may need to be accessed in order to confirm the dates or timeframeassociated with the relationship between the user 102A and the user102B.

At step 606, categories corresponding to the chronological listing aregenerated. As discussed herein, the chronological listing may begenerated for all of the timeframe data associated with therelationships. The chronological listing may then be divided accordingto categories, such as groups, communities, and so forth. For example,the chronological listing for the user 102A may be assigned thecategories of a work group, a college group, and a friends group,associated with the user 102A.

At step 608, the names of individuals corresponding to the categoriesare identified. As shown in FIG. 5, the social timeline page 500 maydisplay the names of individuals, such as other users 102, within groupsor communities. For example, the names of individuals that arecoworkers, classmates, travel companions, and so forth may be displayedunder the relevant category according to the time identifier 502 inwhich the user 102A met or otherwise associated with the individuals.

At step 610, photos corresponding to the identified names are obtained.As discussed herein, the photos 506 may include pictures of each of theusers 102 associated with the identified names or with some of the users102 associated with the identified names or any other photos obtainedfrom the users 102 or provided by the users 102.

At step 612, the social timeline is displayed, for example, asillustrated by the social timeline display page 500. The social timelinecan be updated according to new data, reordered data based on new datesor timeframes provided, and so forth. For example, the user 102A may addthe user 102N as a new friend in the coworkers category. The user 102Nmay then be added to the social timeline according to the dates providedby the user 102A. The user 102N may be a new individual that the user102A has met or the user 102N may be an individual the user 102A hasknown previously, but with whom the user 102A has added a newrelationship.

FIG. 7 is a flow diagram of an exemplary process for generating a socialtimeline. At step 702, a plurality of data items associated with atleast one relationship between users associated with a social networkare received, each data item having an associated time. For example, theuser 102A can provide events and times associated with the events abouta relationship with the user 102B via the relationship editor page 400or via any other interface. The user 102A can provide any type of dataitems about the relationship, such as a type of relationship, eventsassociated with the relationship, a timeframe associated with therelationship and/or events, other users 102 associated with the events,and so forth. As discussed herein, the data may be received from aquestionnaire presented to the users 102 by the relationship editor page400.

At step 704, the data items are ordered according to the associatedtime. As discussed herein, the data provided by the user 102A may beordered to generate a chronological listing. For example, the data aboutthe user A's 102A relationship with the user 102B and the user 102N maybe compared and listed according to dates associated with therelationships with the user 102B and the user 102N. If the user 102B andthe user 102N are in different categories, such as the user 102B is fromwork, while the user 102N dated the user 102A, different chronologicallistings may be generated for each of the user 102B and the user 102N.The data may also be ordered according to one chronological listing thatindicates the timeframes of all of the various relationships.

At step 706, a social timeline is generated according to the ordereddata. As discussed herein, the social timeline may be displayed, forexample, the social timeline page 500 of FIG. 5. The social timeline mayinclude a listing by any increment of time, such as year, month, day,and so forth, of relationships the users 102 have with other users 102.As discussed herein, the social timeline may include all of therelationships, relationships according to categories, and/or individualrelationships. Thus, a different social timeline may be generated and/ordisplayed for each of the users 102.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. For example, any of the elements associated with the socialnetwork engine 106 may employ any of the desired functionality set forthhereinabove. Thus, the breadth and scope of a preferred embodimentshould not be limited by any of the above-described exemplaryembodiments.

1. A computer-implemented method for displaying a social timeline, themethod comprising: maintaining in a computer system a plurality ofrelationships among users in a social networking environment, eachrelationship comprising a connection between at least two users of thesocial networking environment; for at least one relationship, receivingone or more relationship details from at least one of the users in therelationship; generating a social timeline for one or morerelationships, the social timeline comprising a listing of one or moreof the relationship details, the social timeline further comprisingselectable links such that selection of the links provides access toinformation about the relationships associated with the links; anddisplaying the social timeline of the relationships in a graphical userinterface.
 2. The method of claim 1, wherein one or more of the receivedrelationship details comprises a durational time period of therelationship and a category of the relationship.
 3. The method of claim2, wherein the category of the relationship in the received relationshipdetails comprises a characterization of the nature of the relationshipbetween users of the social network.
 4. The method of claim 1, whereinthe social timeline is displayed according to privacy settings selectedby at least one of the users in at least one of the relationships in thesocial timeline.
 5. The method of claim 1, further comprising: enablingthe users connected in the relationships displayed on the socialtimeline to edit the social timeline.
 6. The method of claim 1, furthercomprising: generating stories for the users based on the socialtimeline.
 7. The method of claim 1, wherein the social timeline furthercomprises photos of one or more of the users connected in at least oneof the relationships in the social timeline.
 8. The method of claim 1,wherein the social timeline further comprises one or more events relatedto at least one of the relationships in the social timeline.
 9. A systemfor displaying a social timeline, the system comprising: a socialrelationship editor module configured to maintain in a computer system aplurality of relationships among users in a social networkingenvironment, each relationship comprising a connection between at leasttwo users of the social networking environment; a communicationsinterface configured to, for at least one relationship, receive one ormore relationship details from at least one of the users in therelationship; a social timeline module configured to generate a socialtimeline for one or more relationships, the social timeline comprising alisting of one or more details of the relationships, the social timelinefurther comprising selectable links such that selection of the linksprovides access to information about the relationships associated withthe links; and a display configured to display the social timeline ofthe relationships in a graphical user interface.
 10. The system of claim9, wherein one or more of the relationship details comprises adurational time period of the relationship and a category of therelationship.
 11. The system of claim 10, wherein the category of therelationship in the relationship details comprises a characterization ofthe nature of the relationship between users of the social network. 12.The system of claim 9, wherein the display is configured to display thesocial timeline according to privacy settings selected by at least oneof the users in at least one of the relationships in the socialtimeline.
 13. The system of claim 9, wherein the social timeline moduleis further configured to enable the users connected in the relationshipsdisplayed on the social timeline to edit the social timeline.
 14. Thesystem of claim 9, wherein the social timeline module is furtherconfigured to generate stories for the users based on the socialtimeline.
 15. The system of claim 9, wherein the social timeline furthercomprises photos of one or more of the users connected in at least oneof the relationships in the social timeline.
 16. The system of claim 9,wherein the social timeline further comprises one or more events relatedto at least one of the relationships in the social timeline.
 17. Acomputer program product for displaying a social timeline, the computerprogram product comprising a computer-readable storage medium containingcomputer program code for: maintaining in a computer system a pluralityof relationships among users in a social networking environment, eachrelationship comprising a connection between at least two users of thesocial networking environment; for at least one relationship, receivingone or more relationship details from at least one of the users in therelationship; generating a social timeline for one or morerelationships, the social timeline comprising a listing of one or moredetails of the relationships, the social timeline further comprisingselectable links such that selection of the links provides access toinformation about the relationships associated with the links; anddisplaying the social timeline of the relationships in a graphical userinterface.
 18. The computer program product of claim 17, wherein one ormore of the relationship details comprises a durational time period ofthe relationship and a category of the relationship.
 19. The computerprogram product of claim 18, wherein the category of the relationship inthe relationship details comprises a characterization of the nature ofthe relationship between users of the social network.
 20. The computerprogram product of claim 17, wherein the code for displaying isconfigured to display the social timeline according to privacy settingsselected by at least one of the users in at least one of therelationships in the social timeline.
 21. The computer program productof claim 17, the computer-readable storage medium further containingcomputer program code for: enabling the users connected in therelationships displayed on the social timeline to edit the socialtimeline.
 22. The computer program product of claim 17, thecomputer-readable storage medium further containing computer programcode for: generating stories for the users based on the social timeline.23. The computer program product of claim 17, wherein the socialtimeline further comprises photos of one or more of the users connectedin at least one of the relationships in the social timeline.
 24. Thecomputer program product of claim 17, wherein the social timelinefurther comprises one or more events related to at least one of therelationships in the social timeline.